fix(bug-assess): recompile lock so github guard repos is 'all'#3036
Merged
Conversation
The committed lock file declared compiler v0.79.8 but contained a github
allow-only guard policy with `"repos": "${GITHUB_REPOSITORY}"`. MCP Gateway
v0.3.25 rejects repo-specific values ("allow-only.repos string must be 'all'
or 'public'"), so the agent job failed at "Start MCP Gateway":
failed to register guard for server "github": invalid server guard policy:
allow-only.repos string must be 'all' or 'public'
Recompiling bug-assess.md with gh-aw v0.79.8 deterministically emits
`"repos": "all"` (the gateway-accepted default when min-integrity is set
without an explicit repos scope), confirming the committed lock was stale.
This also reconciles the manifest setup-action SHA with the value already
used in the workflow body.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes the bug-assess agentic workflow failing at the Start MCP Gateway step by updating the compiled workflow lock output to match MCP Gateway v0.3.25’s accepted GitHub guard policy shape.
Changes:
- Recompiled
bug-assess.lock.ymlso the GitHub MCP serverallow-only.reposguard value is"all"(instead of"${GITHUB_REPOSITORY}"), and updated the manifest action SHA to a resolved commit SHA. - Updated
.github/aw/actions-lock.jsonto include the resolved SHA entry forgithub/gh-aw-actions/setup@v0.79.8.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/bug-assess.lock.yml | Updates compiled lock output to use repos: "all" in the GitHub MCP guard policy and pins the setup action to a resolved SHA. |
| .github/aw/actions-lock.json | Adds the corresponding resolved SHA lock entry for github/gh-aw-actions/setup@v0.79.8. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
bug-assessagentic workflow fails at the Start MCP Gateway step (run 27720902903, and the immediate re-run). The gateway container (gh-aw-mcpg:v0.3.25) exits during initialization with:Root cause
bug-assess.lock.ymldeclared compilerv0.79.8but its github MCPallow-onlyguard policy contained:which resolves to
github/spec-kit. MCP Gateway v0.3.25 rejects a specificowner/repoinallow-only.repos— it only accepts the literalallorpublic.Commit 9775c27 ("set min-integrity: none to allow reading external user issues") both added
min-integrity: noneand bumped the gatewayv0.3.22 → v0.3.25, but the committed lock was stale: its guard policy still used the old${GITHUB_REPOSITORY}form (and its manifest setup-action SHA was unresolved while the body already used the resolved SHA). The earlier successful run passed because it ran the prior lock (repos: allvia the runtime lockdown path, gateway v0.3.22).Fix
Recompiled
bug-assess.mdwith the repo's pinnedgh-aw v0.79.8, which deterministically emits"repos": "all"— the gateway-accepted default whenmin-integrityis set without an explicit repo scope — and reconciles the manifest setup-action SHA.min-integrity: noneis preserved, so reading external-user issues still works.gh aw compile bug-assess→ 0 errors, 0 warningsbug-assess.lock.ymland.github/aw/actions-lock.jsonchange.Validation
Re-apply the
bug-assesslabel to a bug issue (or merge and re-trigger) to confirm the gateway starts.Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com